chore(cookbook): improve databases guide#1836
Closed
patricebender wants to merge 9 commits intomainfrom
Closed
Conversation
Contributor
|
@patricebender Meanwhile there are many conflicts. How should we proceed with this PR? |
Contributor
Author
|
lets just close it, bit of a pity that no one cared about this. However, with Daniels recent changes it seems to be obsolete. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR: Make db guides more homogenous.
cds add …overnpm add …in all guidesnewandoldas those terms are outdated pretty quick →cap-js/databasesandlegacyare more accurate